Rules Management - Available Templates

Actions and Templates are rule logic created to ensure the specific wording of a rule is correct, thus enabling the rule to function properly.

The following table provides an alphabetical list of the rule templates that are available in Rules Management, as well as a description of each template, and the recommended Rule Category and Entity to use to author a rule with the template:

Action Template

Purpose

Rule Category/Entity

Accept Promotion Offer

This template enables institutions to automatically accept a promotional offer for a third party or Virtual Capture application based on rule conditions. When this template is executed, the promotional offer is linked to the application, and the Application > Matched Promotion > Offer Decision Status is set to Accepted in the application.

For more information on this template, please see the Promotion Configurations section of the Indirect Processing Overview topic, or the Rule Configuration section of the Promotions in Virtual Capture topic in this guide.

Category: Promotions

Entity: Promotion

Add a Check funding record to a Loan

Action template that is used to create check loan allocations. An allocation amount, payees and memos are able to be defined with this template. Additionally, this template gives rule authors the ability to exclude payees from OFAC.

For more information on this template, please see the Add a Check funding record to a Loan Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.Funding

Add a Collateral

Adds a collateral to a loan application.

Rule authors can configure a rule to include this template, as well as the Execute Rule Set action template, to define the collateral to be added to the application, and then execute the rule set authored to set the specific Collateral fields in the application. For more information, please see the Add a Collateral Rule Vocabulary Template Example in this guide.

Category: Event Processing

Entity: Application, Liability

Add a Collateral Real Estate Order record to a Loan

Used to add a collateral real estate order record to a loan application.

Category: Event Processing

Entity: Application.Collaterals

Add a comment to a counteroffer

This template enables institutions to add comments to a counteroffer.

For more information on this template, please see the Add a comment to a counteroffer Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Add a Discount

Adds a discount in the form of a percentage to the Base Rate used for the Pricing Model.

Category: Pricing

Entity: Application

Add a document to the document set

Adds a document to the document set for CUNA Web Docs.

Category: Document Selection

Entity: Application

Add a Fee

This template adds a loan fee to the application with options for “Prepaid Finance Charge,” “Include in Loan Amount," and "Include in MAPR."

This template only provides the ability to add loan fees to an application. To author a rule that automatically adds fees for an account product, use the Add an Account Product Fee record template.

For more information on this template, please see the Add Fee Rule Vocabulary Template Example in this guide.

Category: Fee

Entity: Application

Add a Fee - OBSOLETE

Adds a loan fee to the collection on the application.

This action template is being phased out as of the 15.01.36 release. Any rules authored with this template will break when it is removed in a future release; therefore, it is recommended that the “Add a Fee” action template is used to author new Fee rules, and replace existing rule logic that uses this template.

Category: Fee

Entity: Application

Add a Fee (Home Equity)

Adds a Home Equity type fee to the application with options for “Prepaid Finance Charge,” “Include in Loan Amount,” “POC Amount,” “Paid By,” and "Customer Selected Provider."

For more information on this template, please see the Add a Fee Rule Vocabulary Template example in this guide.

Category: Fee

Entity: Application

Add a Fee (Home Equity) - OBSOLETE

Adds a Home Equity type of fee with options for “Prepaid Finance Charge,” “Include in Loan Amount,” “POC Amount,” “Paid By,” etc.

This action template is being phased out as of the 15.01.36 release. Any rules authored with this template will break when it is removed in a future release; therefore, it is recommended that the “Add a Fee (Home Equity)” action template is used to author new Fee rules, and replace existing rule logic that uses this template.

Category: Fee

Entity: Application

Add a GL voucher funding record to a Loan

Action template that is used to create general ledger loan allocations. An allocation amount as well as destination general ledger is determined with this template.

For more information on this template, please see the Add a GL voucher funding record to a Loan Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.Funding

Add a GL Voucher funding record to an Account Product

Action template that is used to create a GL Voucher funding record for an account product. The GL Voucher from which funds are transferred as well as the amount to be funded is determined with this template.

For more information on this template, please see the Add a GL Voucher funding record to an Account Product Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.AccountProducts

Add a Liability

Action template that provides the ability to create a liability from within a business rule. Using this template, institutions are able to automatically create liabilities based on events such as a custom field being populated, or the Answer Code and Answer Explanation to declaration questions such as "Do you pay alimony" and "Do you pay child support."

For more information on this template, please see the Add a Liability Template Example in this guide.

Category: Event Processing

Entity: Applicant

Add a Loan Covenant

Adds a loan covenant to the application with options to assign the covenant type, the placeholders to be populated in the covenant description, the validation frequency, the duration, and the next due date.

For more information on this template, please see the Add a Loan Covenant Rule Vocabulary Template example in this guide.

Category: Loan Covenants

Entity: Applicant

Add a Loan Manual To-Do

Enables a rule author to assign a Manual To-Do validation to display a notification and prevents users from rendering a decision, generating document, or disbursing the application until the validation associated with a specific screen is completed.

For more information on this template, please see the Permission Based Loan Manual To-dos Rule Vocabulary Template Example in this guide.

A Manual To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

Category: Validation

Entity: Application

Add a Loan Manual To-Do that is linked to a screen

Enables a rule author to assign a loan Manual To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the validation associated with a specific screen is completed.

A Manual To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

Category: Validation

Entity: Application

Add a Loan Manual To-do that is linked to a screen with Security Groups

Enables a rule author to assign a loan Manual To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the to-do is cleared. Only a member of the assigned security group can provide the information on the screen causing validation to fail.

A Manual To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

Category: Validation

Entity: Application

Add Loan Manual To-Do with Security Groups

Enables a rule author to assign a loan Manual To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the to-do is cleared. Only a member of the assigned security group can provide the information causing validation to fail.

A Manual To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

Category: Validation

Entity: Application

Add a Loan Stipulation Required for Approval

Adds a stipulation to the collection on the application where the IsRequiredToApprove field is set to true. In order to manually approve an application, any stipulations of this type must be either met or waived.

Category: Stipulation

Entity: Application

Add a Loan Stipulation Required for Approval with Security Groups

For more information on this template, please see the Permission Based Loan Stipulations Rule Vocabulary Template example in this guide.

Category: Stipulation

Entity: Application

Add a Loan Stipulation Required for Disbursement

Adds a stipulation to the collection on the application where the IsRequiredToDisburse field is set to true. In order to disburse an application, any stipulations of this type must be either met or waived.

Category: Stipulation

Entity: Application

Add a Loan Stipulation Required for Disbursement with Security Groups

Adds a stipulation to the collection on the application where the IsRequiredToApprove field is set to true. In order to disburse an application, any stipulations of this type can only be met or waived by the assigned security group.

Category: Stipulation

Entity: Application

Add a Loan To-Do

Enables a rule author to assign a loan To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the validation is cleared. A To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

Category: Validation

Entity: Application

Add a Loan To-do that is linked to a screen

Enables a rule author to assign a loan To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the validation associated with a specific screen is cleared. A To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

For more information on this template, please see the Add a To-Do Rule Vocabulary Template Example in this guide.

If a To-Do is linked to a screen, users are able to access the linked screen even if they do not have permission to view the screen. Screen permissions are mainly applied in Workflow Models, where the screen is mapped and provided rights for only certain users to view in the workspace. To-Dos are rules and only perform what is authored in the rule. To-Dos do not touch the security of the screen.

Category: Validation

Entity: Application

Add a Premium

Adds a premium in the form of a percentage to the Base Rate used for the Pricing Model.

Category: Pricing

Entity: Application

Add a Review Indicator

Adds a review indicator to the collection on the application. The name of the review indicator is currently a free-form text field. A recommendation and description must also be entered when adding a review indicator.

Category: Decisioning

Entity: Application

Add a Recurring Fee

Adds a recurring fee to the application with options to assign the fee type, amount, and assessment frequency.

For more information on this template, please see the Add a Recurring Fee Rule Vocabulary Template example in this guide.

Category: Fee

Entity: Application

Add a Stipulation

Enables a rule author to add a stipulation to the application. With this action template, authors may determine:

The type of application to which the stipulations apply, such as loan or account.
The security groups able to meet or waive the stipulations.
The application process which the stipulations must be met prior to executing.

Category: Stipulation or Decisioning

Entity: Application

Add a stipulation to a counteroffer

This template enables institutions to add stipulations to a counteroffer.

For more information on this template, please see the Add a stipulation to a counteroffer Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity:Application

Add a To-do

Enables a rule author to assign a loan or account To-Do validation that displays a notification and prevents users from rendering a decision, generating document, or disbursing the application until the validation is cleared. A To-Do that "is not required," such as a To-Do for Post Disbursement or Post Decline Validation, can also be written using this template.

For more information on this template, please see the Add a To-Do Rule Vocabulary Template Example in this guide.

Category: Validation

Entity: Application

Add attached document to IMM

This template provides the ability to include a document attached to an application in a document set that is sent to IMM for signature or archival.

While this template is always available in the rule application, the template should only be used to author rules for use with the IMM connector.

For more information on this template, please see the Configuring the Connector topic in the IMM Connector Guide.

Category: Document Generation or Event Processing

Entity: Application.AttachedDocuments

Add an Account Product

Adds a required or optional account product to an application.

For more information on this template, please see the Add Required or Optional Account Product Rule Vocabulary Template example in this guide.

Category: Default Values or Event Processing

Entity: Application

Add an Account Product as a Base Share

Adds an account product to an application as a base share.

For more information on this template, please see the Add an Account Product as a Base Share Rule Vocabulary Template example in this guide.

Category: Default Values or Event Processing

Entity: Application

Add an Account Product Deposit funding record to a Loan

Action template that is used to create account product loan allocations. An allocation amount as well as destination account product is determined with this template.

For more information on this template, please see the Add an Account Product Deposit funding record to a Loan Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.Funding

Add an Account Product Discount

This template subtracts the discount percentage from the base rate for the specific account product in order to calculate and set the interest rate for each account product in the application.

Category: Pricing

Entity: Application.AccountProducts

Add an Account Product Fee Record

This template provides the ability to automatically add fees for an account product to the application.

This template only provides the ability to add fees for an account product to the application.

To author a rule that automatically adds loan fees to an application, use the Add a Fee template.

For more information on this template, please see the Add an Account Product Fee Record Rule Vocabulary Template Example in this guide.

Category: Fee

Entity: Application.AccountProducts

Add an Account Product Premium

This template adds a premium percentage to the base rate for the specific account product in order to calculate and set the interest rate for each account product in the application.

Category: Pricing

Entity: Application.AccountProducts

Add an Asset Deposit funding record to a Loan

Action template that is used to create asset deposit loan allocations. An allocation amount as well as destination asset is determined with this template.

For more information on this template, please see the Add an Asset Deposit funding record to a Loan Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.Funding

Add an Internal Transfer funding record to an Account

Action template that is used to create internal transfer account allocations. An allocation amount as well as source account is determined with this template.

For more information on this template, please see the Add an Internal Transfer funding record to an Account Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application.AccountProducts

Add Applicant Recipient to DocuSign Envelope

Adds one or more recipients to a DocuSign envelope. Within this template, rule authors are able to assign the Signing Role, Action, Security Type, and Order for each envelope recipient.

While this template is always available in the rule application, the template should only be used to author rules for use with the DocuSign connector.

Category: ESignatureDefaultValues

Entity: Applicant

Add Collateral Other Owner Recipient to DocuSign Envelope

Adds one or more collateral other owners to a DocuSign envelope as a recipient. Within this template, rule authors are able to assign the Signing Role, Action, Security Type, and Order for each collateral other owner to electronically sign a document envelope in DocuSign.

While this template is always available in the rule application, the template should only be used to author rules for use with the DocuSign connector.

Category: ESignatureDefaultValues

Entity: Collateral.OtherOwners

Add Core Message

Expression template that returns a name/value pair from the Core Interface sets a Core Message alert on an application.

Category: Applicant Import

Entity: Applicant

Add Phone Number for Applicant

Adds a phone number to the phones collection for an applicant.

Category: Any

Entity: Applicant

Add Recipient to Silanis Package

Adds one or more recipients to a Silanis package. Within this template, rule authors are able to assign the Signing Role, Security Type, and Order for each package recipient.

While this template is always available in the rule application, the template should only be used to author rules for use with the OneSpan Sign connector.

Category: ESignatureDefaultValues

Entity: Applicant

Add Vendor Recipient to DocuSign Envelope

Adds the vendor contact for a Merchant Lending application to a DocuSign envelope. Within this template, rule authors are able to assign the Signing Role, Action, Security Type, and Order for the vendor recipient.

While this template is always available in the rule application, the template should only be used to author rules for use with the DocuSign connector and Merchant Lending. For more informtion on this template, please see the section titled Vendor Signer Contact for a DocuSign Envelope in the Configuring the Connector topic of the DocuSign connector guide.

Category: ESignatureDefaultValues

Entity: Application

Assign Adverse Action

Sets the adverse action field on the application. Used when an application is being auto-rejected.

Category: Decisioning

Entity: Application

Assign Application Account Decision

Sets the Account decision for the application. If set to Auto_Approved, Approval processing is executed. If set to Auto_Rejected, Decline processing is executed. Once the application is decisioned, the decision value set here is updated within the AccountDecisionId field.

Category: Decisioning

Entity: Application

Assign Application Loan Decision

Sets the Loan decision for the application. If set to Auto_Approved, Approval processing is executed. If set to Auto_Rejected, Decline processing is executed. Once the application is decisioned, the decision value set here is updated within the LoanDecisionId field.

Category: Decisioning

Entity: Application

Assign Application Status

Sets the status on the application.

Category: Any

Entity: Application

Assign Credit Bureau Sequence

An action template that allows rule based priority selection of Credit Bureaus. This template is used to replace the hard coded bureau selection in a loan application types. Rules can set a Credit Bureau as a 1, 2, or 3. The resulting list of credit bureaus is used in ascending order when performing credit bureau rollover.

Category: Credit Bureau Selection

Entity: Application

Assign Rejected Reason

Adds a reject reason to the collection on the application. Used when an application is being auto-rejected.

Category: Decisioning

Entity: Application

Assign Risk Tier

Set the Risk Tier for the applicant.

Rules that use this action should be written at the Applicant entity. This ensures that the rules are executed and tested for all applicants on the application.

Category: Risk

Entity: Application

Assign to Assignment Group

Associates an application to an Assignment Group.

Category: Assignment

Entity: Application

Assign to Queue

Sets the Queue to which an application is assigned. This action does not pin the application to a queue; therefore, the application can be re-queued based on other rules.

Category: Queuing

Entity: Application

Create a counteroffer

This template enables institutions to define the interval in which countered loan terms and amounts should increase or decrease.

For more information on this template, please see the Create a counteroffer Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Create a counteroffer for manual review

This template enables institutions to define the loan terms and amount of the counteroffer. Upon generation, each counteroffer is flagged for underwriting review.

For more information on this template, please see the Create a counteroffer for manual review Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Decline Promotion Offer

This template enables institutions to automatically decline a promotional offer for a third party or Virtual Capture application based on rule conditions. When this template is executed, the promotional offer is linked to the third party application, and the Application > Matched Promotion > Offer Decision Status is set to Declined in the application.

Category: Promotions

Entity: Promotion

Display Error Message

Adds a message that is displayed to the user. The message is flagged as an error and prevents the user from moving forward. These messages are typically used to enforce user-defined validation.

Category: Any

Entity: Application

Display Information Message

Adds a message that is displayed to the user. The message is flagged as informational and does not prevent the user from moving forward. These messages are typically used as a notification to the user.

Category: Any

Entity: Application

Display Warning Message

Adds a message that is displayed to the user. The message is flagged as a warning and does not prevent the user from moving forward. These messages are typically used as a notification to the user.

Category: Any

Entity: Application

Do Not Update Actual Rate

When the Pricing Model runs, only the Assigned Rate updates. Unless "Do Not Update Actual Rate" Action is used, both the Assigned and Actual Rates update when Pricing runs.

Category: Pricing

Entity: Application

Exclude Liability for Applicant

This is an assignment template used to set the IsExpense flag to false on a specific liability record for the applicant. Rules using this action should be written at the Applicant.Liabilities entity to ensure the rule is executed for each liability for each applicant.

Liabilities where the IsExpense flag is false are not displayed on the Liabilities workflow step.

Category: Trade Processing

Entity: Applicant.Liabilities

Get Address for Applicant Type

Gets the current address of an applicant of the defined type.

Category: Any

Entity: Application

Get Addresses Host Value

Expression template that returns a name/value pair from the Core Interface that the system can then use to populate the value of an address level field in the Temenos application.

Category: Applicant Import

Entity: Addresses

Get Aggregate for Applicant

This is an expression template that easily locates the value of an aggregate within the collection for an applicant. When using this template, an aggregate name must be selected from the list.

To isolate an aggregate for the Primary applicant, first select the Primary Applicant template followed by the Get Aggregate for Applicant template.

Category: Pricing or Decisioning

Entity: Applicant

Get Aggregate for Applicant at Decision

Returns the value of the specified aggregate for each applicant at the time the application was decisioned.

Category: Validation

Entity: Applicant

Get Aggregate for Application

This is an expression template that easily locates the value of an aggregate within the collection on the application. When using this template, an aggregate name must be selected from the list.

Category: Pricing or Decisioning

Entity: Application

Get Aggregate for Application at Decision

Returns the value of the specified aggregate at the time the application was decisioned.

Category: Validation

Entity: Application

Get Applicant Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Applicant level field in the Temenos application.

Category: Applicant Import

Entity: Applicant

Get Applicant Income Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Applicant Income level field in the Temenos application.

While this template is always available in the rule application, the template should only be used to author rules for the UltraData core.

Category: Applicant Import

Entity: Applicant.Income

Get Applicant Reference Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Applicant Reference level field in the Temenos application.

While this template is always available in the rule application, the template should only be used to author rules for the UltraData core.

Category: Applicant Import

Entity: Applicant.Reference

Get Application Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Application level field in the Temenos application.

Category: Applicant Import

Entity: Application

Get Application.AccountProducts Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Application.AccountProduct level field in the Temenos application.

Category: Applicant Import

Entity: Application.AccounProducts

Get Asset Host Value

Expression template that returns a name/value pair from the core interface, which the system can then use to populate the value of an Asset level field in the Temenos application.

Category: Applicant Import

Entity: Assets

Get Average Score for Application

This is an expression template that easily locates the value of the Average Score within the collection on the application. When using this template, a Score name must be selected from the list.

The Average score is calculated during credit report processing by taking an average of the same score values across all applicants on the application.

Category: Risk, Pricing, or Decisioning

Entity: Application

Get Branch for User

This is an expression template that easily locates the branch that is associated to a particular system user. You can select from current user, created by, decisioned by, pitched by, debt protection selected by, disbursed by, or a specific username.

Category: Any

Entity: Application

Get Collateral Other Owner Host Value

This expression template easily locates and imports data from the core for each collateral other owner on an application.

While this template is always available in the rule application, the ability to import data for collateral other owners is only supported for certain cores. For more information on whether this ability is supported, please see the applicable core connector guide for the institution.

Category: Applicant Import

Entity: Collateral.OtherOwners

Get Collateral Other Owner Asset Host Value

This expression template easily locates and imports data from the core for each asset related to each collateral other owner on an application.

While this template is always available in the rule application, the ability to import asset data for collateral other owners is only supported for certain cores. For more information on whether this ability is supported, please see the applicable core connector guide for the institution.

Category: Applicant Import

Entity: CollateralOtherOwner.Assets

Get Credential for User

This expression template returns the credentials associated to with a particular system user. Within this template, authors can select the credential type and user from lists. When this template executes, the user's credential id is returned.

Category: Any

Entity: Application

Get Full Name for User

Get Full Name of the user.

Category: Any

Entity: Application

Get First Collateral by Collateral Type

This is an expression template that easily locates that first collateral record on the application for a specific collateral type. Use this template when writing a rule or decision table at the Application entity and needing to add a condition regarding the primary or first piece of collateral on the application.

Category: Pricing or Decisioning

Entity: Application

Get First Collateral by Vehicle Type

This is an expression template that easily locates that first collateral record on the application for a specific vehicle type. Use this template when writing a rule and when adding a condition regarding and needing to add a condition regarding the primary or first piece of collateral on the application.

Category: Disbursement

Entity: Application

Get GL Account for Branch

This is an expression template that easily locates the branch that is associated to a particular branch. You can select from originating branch, closing branch, or the branch associated to a system user.

Category: Risk, Pricing, or Decisioning

Entity: Application

Get High Score for Application

This is an expression template that easily locates the value of the High Score within the collection on the application. When using this template, a Score name must be selected from the list.

The High score is calculated during credit report processing by taking the highest of the same score values across all applicants on the application.

Category: Disbursement

Entity: Application

Get HostID1 for User

An expression template that returns the HostID 1 value for the user that is passed to the template. The HostID 1 value is maintained on the user management screen.

Category: Disbursement

Entity: Application

Get HostID2 for User

An expression template that returns the HostID 2 value for the user that is passed to the template. The HostID 2 value is maintained on the user management screen.

Category: Disbursement

Entity: Application

Get Liability Host Value

Expression template that returns a name/value pair from the Core Interface that the system can then use to populate the value of a liability level field in the Temenos application.

Category: Applicant Import

Entity: Liabilities

Get Liability Pattern Count by Category

Expression template that returns a count of matching liabilities based on a trade category, time-frame, trade indicator and number of occurrences.

Category: Decisioning

Entity: Applicant

Get Liability Pattern Count

Expression template that returns a count of matching liabilities based on a time-frame, trade indicator and number of occurrences.

Category: Decisioning

Entity: Applicant

Get Liability Pattern Count By Category for Application

An expression template that returns the liability count according to category.

Category: Decisioning

Entity: Application

Get Liability Pattern Count for Application

An expression template that returns the liability count.

Category: Decisioning

Entity: Application

Get Low Score for Application

This is an expression template that easily locates the value of the Low Score within the collection on the application. When using this template, a Score name must be selected from the list.

The Low score is calculated during credit report processing by taking the lowest of the same score values across all applicants on the application.

Category: Risk, Pricing, or Decisioning

Entity: Application

Get Phone Host Value

Expression template that returns a name/value pair from the Core Interface that the system can then use to populate the value of a phone level field in the Temenos application.

Category: Applicant Import

Entity: Phones

Get Phone Number for Applicant

This is an expression template that easily locates a particular phone (e.g.: home, work) for an applicant.

Category: Any

Entity: Applicant

Get Ratio for Applicant

This is an expression template that easily locates the value of a ratio within the collection for an applicant. When using this template, a ratio name must be selected from the list.

Category: Pricing or Decisioning

Entity: Applicant

Get Ratio for Applicant at Decision

Returns the value of the specified ratio for each applicant at the time the application was decisioned.

Category: Validation

Entity: Applicant

Get Ratio for Application

This is an expression template that easily locates the value of a ratio within the collection on the application. When using this template, a ratio name must be selected from the list.

Category: Pricing or Decisioning

Entity: Application

Get Ratio for Application at Decision

Returns the value of the specified ratio at the time the application was decisioned.

Category: Validation

Entity: Application

Get Score for Applicant

This is an expression template that easily locates the value of a score within the collection for an applicant. When using this template, a score name must be selected from the list.

To isolate a ratio for the Primary applicant, first select the Primary Applicant template followed by the Get Ratio for Applicant template.

Category: Risk, Pricing, or Decisioning

Entity: Applicant

Include Application for Decisioning

Used to determine if an associated application of an applicant should be considered in Decisioning the current application.

Category: Decisioning

Entity: AssociatedApplications

Include Liability for Applicant

This is an assignment template used to set the IsExpense flag to true on a specific liability record that has already been systematically excluded for the applicant. Rules using this action should be written at the Applicant.Liabilities entity to ensure the rule is executed for each liability for each applicant.

Category: Trade Processing

Entity: Applicant

Is Self Employed

This is an expression template that easily identifies whether an applicant is self-employed by looking up the Self Employed flag in the Income collection off of the applicant record. This template could be used in conjunction with the "Primary Applicant" template to determine if specifically the Primary Applicant is self-employed.

Category: Any

Entity: Application

Logged in User it

The logged-in user performing the action.

Category: Any

Entity: Application

Logged in User is Assigned to Security Group

The security group of the logged-in user.

Category: Any

Entity: Application

Number of Credit Report Inquiries

Expression template that returns a count of inquiries reported on a credit report for an applicant.

Category: Decisioning

Entity: Applicant

Pitch Cross-sell Product

Adds a Cross-sell Product to the collection on the application to be pitched to the applicant. This action should be used to pitch Non-Loan Cross-sell Products. The Amount is obtained from the Cross-sell Product management screen.

Category: Cross-sell Products

Entity: Application

Pitch Cross-sell Product with Amount

Adds a Cross-sell Product with the specified Amount to the collection on the application to be pitched to the applicant. This action can be used to pitch both Loan and Non-Loan Cross-sells.

If the Cross-sell being pitched is a Non-loan, the amount entered is used instead of the amount defined on the Cross-sell Product management screen.
If the Cross-sell being pitched is a Loan, the amount entered is used as the Principal for the Cross-sell. In addition, the Number of Payments and Frequency entered on the Cross-sell Product management screen is used. Loan Cross-sells are priced, amortized, and decisioned to determine if the applicant is automatically approved for the product. If the applicant is approved, the Cross-sell is displayed on the Cross-sell screen. If the applicant is not approved, the Cross-sell is not displayed on the Cross-sell screen.

Category: Cross-sell Products

Entity: Application

Primary Application

This is an expression template that easily isolates the primary applicant on the application. Once selected, the field list for the applicant entity is available.

Category: Any

Entity: Application

Primary Applicant's Current Address

This is an expression template that easily isolates the primary applicant on the application and then isolates their current address. Once selected, the field list for the address entity is available.

Category: Any

Entity: Application

Processing User Is

Temenos Infinity's processing user.

Category: Any

Entity: Application

Processing User is Assigned to Security Group

The security group for Temenos Infinity's processing user.

Category: Any

Entity: Application

Remove GL Voucher Funding Records

Action template that removes all general ledger fund allocations from an application. Within this template, rule authors are able to select the GL Voucher Code that is to be removed from an application's funding from a drop-down list.

Category: Event Processing

Entity: Application.Funding

Require Approval Override

This action is used when the current user is not authorized to approve the application. Based on criteria, this action is used to send a message from the rules engine back to LOS, requiring an authorized user to log in to process the approval.

This action is typically used in conjunction with the "Get Current User" or "Get Current User's Security Group" templates.

Category: LOA Limits

Entity: Application

Send a Notification

Adds a notification to the application in progress. This template can be used to display custom notifications in the workspace when an event occurs in the application. Rule authors are able to select:

The text to be included in the notification.
Whether the notification is an error, a success message, informational or urgent.

Category: Event Processing

Entity: Application

Send a Notification to Notification Group

Sends a notification to the user(s) assigned to a notification group. Rule authors are able to select:

The text to be included in the notification.

Can be a standard statement or a statement that includes a concatenation of application data. Including the application field “RecentComment to the text enables application comments to display within the notification.

Whether the notification is informational or urgent.
The desired notification group(s) from a list that populates with all groups identified in System Management > Groups > Notification Groups.

For more information on this template, please see the Send a Notification to Notification Group Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Send a Notification to Vendor Representative

Sends a notification to the user designated as the representative of vendor that submitted the application.

Vendor Representatives are identified within System Management > Origination > Loan > Vendor Management.

Rule authors are able to select:

The text to be included in the notification.

Whether the notification is informational or urgent.

For more information on this template, please see the Send a Notification to Vendor Representative Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Send Email to Address

Sends an email to the user who created the application. Provides selection from a list of email templates configured in Temenos Infinity.

Category: Decisioning

Entity: Application

Send Email to Applicant

Sends an email to applicants by selecting the applicant type to receive the email. Provides selection from a list of email templates configured in Temenos Infinity.

Category: Decisioning

Entity: Application

Send Email to Created By

Sends an email the user that created the application. Provides selection from a list of email templates configured in Temenos Infinity.

Category: Decisioning

Entity: Application

Send Email to Decisioned By

Sends an email the user who decisioned the application. Provides selection from a list of email templates configured in Temenos Infinity.

Category: Decisioning

Entity: Application

Send Email to Notification Group

Sends an email to the user(s) assigned to a notification group. Rule authors are able to select:

The desired email template from a list that populates with all email templates configured in System Management > Origination > Email Templates.
The desired notification group(s) from a list that populates with all groups identified in System Management > Groups > Notification Groups.

For more information on this template, please see the Send Email to Notification Group Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Send Email to Vendor Representative

Sends an email to the user designated as the representative of the vendor that submitted the application.

Vendor Representatives are identified within System Management > Origination > Loan > Vendor Management.

When authoring the rule, authors are able to select the desired email template from a list that populates with all email templates configured in System Management > Origination > Email Templates.

For more information on this template, please see the Send Email to Vendor Representative Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Set Account Document set

This template enables rule authors to define the default IMM document set for the account product(s) on an application.

Category: Document Selection

Entity: Application.AccountProducts

Set Account Product Host Value

This action is used to set a name/value pair using a name, and then up to five value fields for account product applicants. The usage of the value fields is dependent upon the name used. The host values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the Core Interface, and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Application.AccountProducts

Set Account Product Applicant Host Value

Category: Disbursement

Entity: Application.AccountProducts

Set Account Product Fees Host Value

This action is used to send information to the core for the fees assigned to each account product on the application. This template allows institutions to set a name/value pair using a name, and then up to five value fields for account product fees. The usage of the value fields is dependent upon the name of the host value. The host values collection is then interpreted as necessary by the active core interface. Specific values in the name field are filtered by the core interface, and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Application.AccountProduct.Fees

Set Account Product Fees Document Processing Field

This template is used to set tags for account product fees in IMM documents.

Category: Document Generation

Entity: Application.AccountProduct.Fees

Set Account Product Funding Host Value

This action is used to set a name/value pair using a name and then up to five value fields for account product funding. The usage of the value fields is dependent upon the name used. The host values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the Core Interface, and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Application.AccountProducts or Application.AccountProducts.ApplicantMappings

Set Action Editability

This template is used to refine Editability permissions. Rule authors are able to use this template to grant or revoke permissions to perform an action.

Category: Editability

Entity: Application

Set Address Document Processing Field

Used to add custom fields to be sent to either IMM or CUNA Web Docs for document processing.

Category: Document Generation

Entity: Addresses

Set Address Host Value

This action is used to set a name/value pair using a name and then up to five value fields. The usage of the value fields is dependent upon the name used. The host values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the Core Interface, and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Addresses

Set Applicant Disbursement Value

This action is used to set a name/value pair, using a name and then up to five value fields. The usage of the value fields is dependent upon the name used. The disbursement values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the core interface, and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Applicant

Set Applicant Document Processing Field

Used to add custom fields to be sent to either IMM or CUNA Web Docs for document processing.

Category: Document Generation

Entity: Applicant

Set Applicant Host Value

This action is used to set a name/value pair, using a name and then up to five value fields. The usage of the value fields is dependent upon the host value name. The host value collection is then interpreted as necessary by the core interface that is active to send a specific value to the core.

Category: Disbursement

Entity: Applicant

Set Applicant Host Value for Applicant

Category: Disbursement

Entity: Application.AccountProducts.ApplicantMappings

Set Applicant Income Host Value

While this template is always available in the rule application, the template should only be used to author rules for the UltraData core.

Category: Get New Member and Disbursement

Entity: Applicant.Incomes

Set Applicant Reference Host Value

While this template is always available in the rule application, the template should only be used to author rules for the UltraData core.

Category: Get New Member and Disbursement

Entity: Applicant.References

Set Applicant.Assets Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Applicant.Assets

Set Applicant.Incomes Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Applicant.Incomes

Set Applicant.Liabilities Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Applicant.Liabilities

Set Applicant.References Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Applicant.References

Set Application Disbursement Value

This action is used to set a name/value pair, using a name and then up to five value fields. The usage of the value fields is dependent upon the name used. The disbursement values collection is then interpreted as necessary by the core interface that is active. Specific values in the name field are filtered by the core interface and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Application

Set Application Document Processing Field

Used to add custom fields to be sent to either IMM or CUNA Web Docs for document processing.

Category: Document Generation

Entity: Application

Set Application Host Value

This action is used to set a name/value pair, using a name and then up to five value fields. The usage of the value fields is dependent upon the name used. The host values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the Core Interface and then the value fields are utilized as necessary.

Category: Disbursement

Entity: Application

Set Application.AccountProducts Document Processing Field

Used to add custom fields to be sent to either IMM or CUNA Web Docs for document processing.

Category: Document Generation

Entity: Application.AccountProducts

Set Application.AccountProduct.Fundings Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.AccountProduct.Fundings

Set Application.AggregateAnalysisList Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.AggregateAnalysisList

Set Application.Asset Host Value

Category: Disbursement

Entity: Application.Assets

Set Application.Collaterals Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.Collaterals

Set Application.Fees Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.Fees

Set Application.Fundings Document Processing Field

Used to add custom fields to be sent to either IMM or CUNA Web Docs for document processing.

Category: Document Generation

Entity: Application.Fundings

Set Application.Fundings Host Value

This action is used to set a name/value pair using a name and then up to five value fields for a loan funding record. The usage of the value fields is dependent upon the name. The host values collection is then interpreted as necessary by the Core Interface that is active. Specific values in the name field are filtered by the Core Interface, and then the value fields are applied as necessary.

Category: Disbursement

Entity: Application.Fundings

Set Application.RejectionReasons Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.RejectionReasons

Set Application.Stipulations Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.Stipulations

Set Application.TradeIns Document Processing Field

Used to provide custom data to IMM for use in forms.

Category: Document Generation

Entity: Application.TradeIns

Set Application.Transfers Host Value

Used to send data for each transfer record that is added to an application for an account product to the core.

Category: Disbursement

Entity: Application.Transfers

Set Asset Document Processing Field

Used to provide custom data to CUNA Web Docs step for an asset.

Category: Document Generation

Entity: Assets

Set Authorized User Host Value

Used to set the value of fields for each authorized user on an application using a host value name and then up to five value fields. The usage of the value fields are dependent upon the host value name being used, which is then interpreted by the active core interface.

Category: Get New Member Account or Disbursement

Entity: AuthorizedUser

Set Authorized User Address Document Processing Field

Used to send custom data for authorized user address records to a third party document processing provider for use in forms.

Category: Document Generation

Entity: AuthorizedUser.Addresses

Set Authorized User Address Host Value

Used to set the value of fields for each authorized user address record on an application using a host value name and then up to five value fields. The usage of the value fields are dependent upon the host value name being used, which is then interpreted by the active core interface.

Category: Get New Member Account or Disbursement

Entity: AuthorizedUser.Addresses

Set Authorized User Document Processing Host Value

Used to send custom data for authorized users to a third party document processing provider for use in forms.

Category: Document Generation

Entity: AuthorizedUser

Set Authorized User Phone Document Processing Field

Used to send custom data for authorized user phone records to a third party document processing provider for use in forms.

Category: Document Generation

Entity: AuthorizedUser.Phones

Set Authorized User Phone Host Value

Used to set the value of fields for each authorized user phone record on an application using a host value name and then up to five value fields. The usage of the value fields are dependent upon the host value name being used, which is then interpreted by the active core interface.

Category: Get New Member Account or Disbursement

Entity: AuthorizedUser.Phones

Set Average Score Recommendation

This is an assignment template which is used to set the recommendation (or indicator) on the average value across all applicants for a specific Credit Bureau Score (e.g. Risk Model). When using this template, it is important to select the desired score from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

This action is typically combined with the Get Average Score for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Application

Set Collateral Document Processing Field

Used to provide custom data to either IMM or CUNA Loanliner for a collateral.

Category: Document Generation

Entity: Collateral

Set Collateral Host Value

Category: Disbursement

Entity: Collateral

Set Collateral.HousingExpenses Document Processing Field

Used to provide custom data for a collateral to IMM for use in forms.

Category: Document Generation

Entity: Collateral.HousingExpenses

Set Collateral.HousingExpenses Host Value

Category: Disbursement

Entity: Application.Collateral.HousingExpense

Set Collateral.Liens Document Processing Field

Used to provide custom data for a collateral to IMM for use in forms.

Category: Document Generation

Entity: Collateral.Liens

Set Collateral Other Owner Host Value

This template is used to set host values in the core for each collateral other owner on an application.

While this template is always available in the rule application, the ability to set host values for collateral other owners is only supported for certain cores. For more information on whether this ability is supported, please see the applicable core connector guide for the institution.

Category: Get New Member Account and Disbursement

Entity: Collateral.OtherOwners

Set Collateral.OtherOwners Document Processing Field

Used to provide custom data for a collateral to IMM for use in forms.

Category: Document Generation

Entity: Collateral.OtherOwners

Set Collateral Other Owner Asset Document Processing Field

Used to provide custom data for collateral other owner assets to IMM for use in forms.

While this template is always available in the rule application, the ability to populate data for collateral other owner assets is only supported for certain cores. For more information on whether this ability is supported, please see the applicable core connector guide for the institution.

Category: Document Generation

Entity: CollateralOtherOwner.Assets

Set Collateral Real Estate Orders Document Processing Field

Used to send custom data to IMM for use in documents.

Category: Document Generation

Entity: Collateral.CollateralRealEstateOrders

Set Collateral Real Estate Orders Host Value

Used to set host values for the collateral real estate orders on an application in order to automatically map data from a third party to a collateral real estate order in the Temenos application.

Category: Event Processing

Entity: Collateral.CollateralRealEstateOrders

Set Collection Editability

This template is used to refine Editability permissions. Rule authors are able to use this template to grant or revoke permissions to add, edit, or delete collection members.

Category: Editability

Entity: Application

Set Comment Document Processing Field

Used to send custom data for comments to a third party document processing provider for use in forms.

Category: Document Generation

Entity: Comment

Set counteroffer priority

This template enables institutions to define which loan term should be prioritized when creating counteroffers.

This does not apply for the “Create a counteroffer for manual review” rule template.

For more information on this template, please see the Set counteroffer priority Rule Vocabulary Template example in this guide.

Category: Event Processing

Entity: Application

Set Credit Score Document Processing Field

Used to send custom data for applicant credit scores to a third party document processing provider for use in forms.

Category: Document Generation

Entity: Applicant.Scores

Set Document Header

Set the document Header to be sent for CUNA Loanliner documents.

Category: Document Generation

Entity: Application

Set Document Language

Set the document Language to be sent for CUNA Loanliner documents.

Category: Document Generation

Entity: Application

Set Document Logo

Set the document Logo to be sent for CUNA Loanliner documents.

Category: Document Generation

Entity: Application

Set Document Set

This template enables rule authors to define the default IMM document set.

Category: Document Selection

Entity: Application

Set Field Editability

This template is used to refine Editability permissions. Rule authors are able to use this template to grant or revoke permissions to add, edit, or delete field values.

Category: Editability

Entity: Application

Set Funding Document Processing Field

Used to provide custom data to CUNA Loanliner for funding.

Category: Document Generation

Entity: Funding

Set High Score Recommendation

This is an assignment template which is used to set the recommendation (or indicator) on the high value across all applicants for a specific Credit Bureau Score (e.g. Risk Model). When using this template, it is important to select the desired score from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

This action is typically combined with the Get High Score for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Application

Set Income Document Processing Field

Used to provide custom data to CUNA Web Docs step for an income.

Category: Document Generation

Entity: Incomes

Set Liability Document Processing Field

Used to provide custom data to CUNA Web Docs step for a liability.

Category: Document Generation

Entity: Liabilities

Set Loan Covenant Document Processing Field

Used to provide custom data to IMM for the loan covenants associated with the applicants on an application.

Category: Document Generation

Entity: Applicant.LoanCovenants

Set Loan Covenant Host Value

Used to set the value of fields for each loan covenant associated with the applicants on an application using a host value name, and then up to five value fields. The usage of the value fields are dependent upon the host value name being used, which is then interpreted by the active core interface.

Category: Disbursement

Entity: Applicant.LoanCovenants

Set Low Score Recommendation

This is an assignment template which is used to set the recommendation (or indicator) on the low value across all applicants for a specific Credit Bureau Score (e.g. Risk Model). When using this template, it is important to select the desired score from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

This action is typically combined with the Get Low Score for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Application

Set Phone Document Processing Field

Used to provide custom data to either IMM or CUNA Web Docs step for a phone.

Category: Document Generation

Entity: Phones

Set Phone Host Value

Category: Disbursement

Entity: Phones

Set Recurring Fees Document Processing Field

Used to provide custom data to IMM for the recurring fees on an application.

Category: Document Generation

Entity: Application.RecurringFees

Set Recurring Fees Host Value

Used to set the value of fields for each recurring fee on an application using a host value name, and then up to five value fields. The usage of the value fields are dependent upon the host value name being used, which is then interpreted by the active core interface.

Category: Disbursement

Entity: Application.RecurringFees

Set Score Recommendation for Applicant

This is an assignment template which is used to set the recommendation (or indicator) on the value for a specific Credit Bureau Score (e.g. Risk Model). When using this template, it is important to select the desired score from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

Rules using this action should be written at the Applicant entity to ensure the rule is executed for each applicant.

This action is typically combined with the Get Low Score for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Applicant

Set the Aggregate for the Applicant

Used to set the value of a specific applicant-level aggregate. The specified aggregate is added to the Aggregates Collection for the applicant with the value as calculated by the specified formula. Rules using this action should be written at the Applicant entity to ensure the rule is executed for each applicant.

When using this template, it is important to select the desired aggregate.

Category: Aggregates

Entity: Applicant

Set the Aggregate Recommendation for the Applicant

This is an assignment template which is used to set the recommendation (or indicator) on a specific applicant-level aggregate. When using this template, it is important to select the desired aggregate from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

Rules using this action should be written at the Applicant entity to ensure the rule is executed for each applicant.

This action is typically combined with the Get Aggregate for Applicant template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Applicant

Set the Aggregate for Application

Used to set the value of a specific application-level aggregate. The specified aggregate is added to the aggregates collection on the application with the value as calculated by the specified formula.

When using this template, it is important to select the desired aggregate.

Category: Aggregates

Entity: Application

Set the Aggregate Recommendation for the Application

This is an assignment template which is used to set the recommendation (or indicator) on a specific application-level aggregate. When using this template, it is important to select the desired aggregate from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the aggregate.
A recommendation of "maybe" results in a yellow indicator for the aggregate.
A recommendation of "bad" results in a red indicator for the aggregate.

This action is typically combined with the Get Aggregate for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Application

Set the Answer for a HYLS Question

Used to automatically set the answer for a HYLS question based on custom rule logic.

While this template is always available in the rule application, the template should only be used to author rules that execute during the loan application process for the HYLS connector.

Category: Event Processing

Entity: Applicant

Set the <Lenders Protection action> for the application to <Value>

This template enables rule authors to set the Lenders Protection action to:

Apply Results to the Application.
Apply Results to the Application and Approve.
Create new Counteroffer.
Create new Counteroffer and Accept.

Category: Event Processing

Entity: Application

Set the Maximum Interest Rate

This template is used to identify the maximum interest rate a loan application may not exceed regardless of the premiums added, if rule criteria is met.

Category: Pricing

Entity: Application

Set the Minimum Interest Rate

This template is used to identify the minimum interest rate a loan application may not exceed regardless of the discounts applied, if rule criteria is met.

Category: Pricing

Entity: Application

Set the Ratio for the Applicant

Used to set the value of a specific applicant-level ratio. The specified ratio is added to the ratios collection for the applicant with the value as calculated by the specified formula. Rules using this action should be written at the Applicant entity to ensure the rule is executed for each applicant.

When using this template, it is important to select the desired ratio.

Category: Ratios

Entity: Applicant

Set the Ratio Recommendation for the Applicant

This is an assignment template which is used to set the recommendation (or indicator) on a specific applicant-level ratio. When using this template, it is important to select the desired ratio from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the ratio.
A recommendation of "maybe" results in a yellow indicator for the ratio.
A recommendation of "bad" results in a red indicator for the ratio.

Rules using this action should be written at the Applicant entity to ensure the rule is executed for each applicant.

This action is typically combined with the Get Ratio for Applicant template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Applicant

Set the Ratio for the Application

Used to set the value of a specific application-level ratio. The specified ratio is added to the ratios collection on the application with the value as calculated by the specified formula.

When using this template, it is important to select the desired ratio.

Category: Ratios

Entity: Application

Set the Ratio Recommendation for the Application

This is an assignment template which is used to set the recommendation (or indicator) on a specific application-level ratio. When using this template, it is important to select the desired ratio from the list and select the appropriate recommendation (good, maybe, bad).

A recommendation of "good" results in a green indicator for the ratio.
A recommendation of "maybe" results in a yellow indicator for the ratio.
A recommendation of "bad" results in a red indicator for the ratio.

This action is typically combined with the Get Ratio for Application template, where the "Get" is used in the condition portion of the rule and the "Set" is used in the action portion.

Category: Decisioning

Entity: Application

Set the value of a field

This action template is used to set the value of one field in an application to the value of another field.

Category: Any

Entity: Any

Stop Processing Application

This action is used during the execution of the Decision Model to determine whether or not the next stage of rules should be processed.

If a stop processing action is returned, the next stage is NOT executed.
If a stop processing action is not returned, the next stage of the decision model is executed.

When all stages have been processed or a stop processing action is returned, the system looks at the decision. If the Decision is set to Auto Approved, then Approval processing is run. If the Decision is set to Auto Rejected, then Rejection processing runs.

Category: Decisioning

Entity: Application

The Applicant with the [Highest/Lowest] Aggregate Value

This action template is used to find the applicant on the application with the highest or lowest value for the identified aggregate.

For more information on this template, please see the Rule Vocabulary Template example for The Applicant with the [Highest/Lowest] Aggregate Value in this guide.

Category: Any

Entity: Application

The Applicant with the [Highest/Lowest] Ratio Value

This action template is used to find the applicant on the application with the highest or lowest value for the identified ratio.

For more information on this template, please see the Rule Vocabulary Template example for The Applicant with the [Highest/Lowest] Ratio Value in this guide.

Category: Any

Entity: Application

The Applicant with the Highest Score

Finds the applicant who has the highest credit score.

Category: Any

Entity: Application

The Code for a Lookup Value

Finds the lookup code for a lookup value.

Category: Any

Entity: Application

The Display for a Lookup Value

Finds the lookup display for a lookup value.

Category: Any

Entity: Application

The Execution Source

Enables customers to select where a rule executed from (for example Screen, Decision and so on) via the Validation Location value list. This allows institutions to write one rule with the one condition, and then conditionally throw the warning or error/to-do depending on where the rule was fired from.

Category: Validation

Entity: Application

The Field for a Company

Allows users to author rule logic with company fields from their institution’s address book.

Category: Any

Entity: Application

The Field for a User

Finds additional data for a user.

Category: Any

Entity: Application

The Number in Words

Returns a number in words. For example, 134 returns as “One hundred and thirty four.”

Category: Document Generation

Entity: Application

The Segmentation Code Category

Expression template that returns the applicants' segmentation code.

If new segmentation values are added, the user must sync lookups.

The Selected Document Set

Returns the document set selected in DocumentSelection rules.

Category: Validation

Entity: Application

The Value for the Active Valuation

An expression that returns the selected value (such as: Market Value, Trade In Value, and so on) for the last valuation executed.

Category: Validation

Entity: Application

The Value for the Replacement Cross-sell Liability

Obtains the value of a replacement Cross-sell liability.

Category: Cross-sell Generation

Entity: Application